An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi everyone, Thanks in advance to anyone who shares their experience.

Hi, I'm the founder of a small independent mobile app company based in Istanbul, Turkey. I'm sharing this because I'm trying to understand whether anyone else has experienced something similar and whether there are any realistic paths forward after a final Apple Developer Program termination. In April 2026, our app received several App Review rejections. We addressed the issues raised by Apple and submitted updated versions of the app as requested. On April 27, 2026, we received a Pending Termination Notice alleging App Review circumvention. We submitted a formal appeal on April 28 and followed up with additional information and documentation on May 15. On June 2, Apple informed us that our appeal was insufficient and that our membership would be terminated. What caught my attention was that the same communication also stated that submitting a reinstatement request could potentially lead to reconsideration. I took that seriously. We immediately shifted our focus toward a complete compliance review of the app, brought in outside assistance, and reviewed everything we could think of: app metadata, screenshots and marketing assets, user flows, source code, business logic, and third-party integrations. The changes were not cosmetic. Entire features were removed, workflows were redesigned, and significant parts of the application's architecture were revised. Our goal was to address every concern we could identify and submit a comprehensive reinstatement request. Then, on June 6, before we were able to complete and submit that request, we received the final termination notice. To be clear, I'm not claiming Apple made the wrong decision, nor am I posting this to generate outrage. What I found difficult to understand was being told that reinstatement could be considered, investing significant time and resources into preparing that submission, and then receiving a final termination before having the opportunity to submit it. For context: We never used external payment systems. We never purchased or manipulated ratings or reviews. We never distributed binaries hidden from App Review. We never intentionally attempted to deceive Apple or bypass review procedures. I'm 24 years old and this is my first company. Looking back, I can see that some of my decisions came down to inexperience. That's exactly why I took the reinstatement process seriously. I wanted to fix what I could. A few questions: Has anyone received reconsideration after a final Apple Developer Program termination? Has anyone experienced receiving a final termination while actively preparing a reinstatement request? Are there any official communication channels available once App Store Connect access has been removed? Thank you for reading. Batuhan Özdemir Founder, Liquid Apps Team ID: 7K3Z69D85W

We are stuck in AppStoreConnect limbo. We have a new subscription group + two Subscriptions in Ready To Review state in appstoreconnect, but Apple Review rejected our latest app version because they weren't included with the version. Our app version has been rejected for a few issues before this which maybe broke something. When I go to edit the version, there is no Subscriptions & Purchases section to add them for review. I tried editing the subscriptions and subscription group localization to see if that got it out of Waiting For Review state or showed the version section but no luck. So we can't add the Subscriptions for review and we are rejected from App Review if we don't. I submitted an Apple support email 8 days ago and haven't received any response. Does anyone know of a way to get this unblocked?

Hi everyone, I’m trying to understand if what I’m seeing in App Store Connect is normal, or if there’s something I should check on my side. I submitted an iOS 1.2 app version for App Review and I also submitted a TestFlight beta build around the same time. Both are still showing as Waiting for Review. The app version was submitted Thursday at around 10:59 PM, and the beta build was submitted Thursday at around 6:48 PM. Usually my beta builds have moved much faster than this, so I’m not sure if this is just current review backlog or if having both the app version and beta build waiting at the same time can slow things down. A few details: App: Mossly: Plant Care Journal Platform: iOS Version: iOS 1.2 Beta build: iOS 1.2 (40) Both currently show: Waiting for Review I haven’t received any message from App Review asking for more information. Has anyone else seen TestFlight beta review and App Review sit in “Waiting for Review” for several days at the same time? Is there anything I can do besides wait, or any setting/submission state I should double-check? Thanks.

Hi Apple, I'm reaching out because my app Lynup (Bundle ID: ai.lynup.app, Apple ID: 6766385801) has been stuck in "Waiting for Review" since May 6, 2026 — that's now over 19 days with no movement. Here's what I've already tried: Submitted an expedited review request — twice Opened a support ticket with App Review (Case ID: 102892962160) on May 18, 2026 Despite both actions, the status hasn't changed and I haven't received any meaningful update beyond the initial acknowledgment. This is a first submission and the delay is significantly impacting our launch timeline. Any help, advice, or update would be greatly appreciated. Thanks in advance.

Hello, Our app Hook — Smart Message Assistant has been stuck in “Waiting for Review” since June 9, 2026 — 8 days after resubmission addressing all issues raised under Guideline 3.1.2(c) (Subscriptions). Timeline: • June 8: Rejected under Guideline 3.1.2(c) • June 9: Resubmitted with all issues resolved June 9 onwards: Stuck in “Waiting for Review” with no movement We have submitted 3 expedited review requests, all approved. We contacted Developer Support via email and through App Store Connect messages with no response. We are a small team with an active marketing campaign dependent on this launch. Every day of delay has direct business impact. Could the App Review team please investigate this submission? Thank you, Eden

I am writing to follow up regarding the reactivation of our Apple Developer account. We paid the amount requested for the reactivation of the account on the 6 of July and have not yet received any green light to go ahead, please can anyone tell me what to do?

Hello. We have recently submitted for review an app, which has in it Shopify Customer Account API, which allows users to login using a OTP (currently a 6 digit code) received in their email. The login itself uses OAuth and that API provides access to customer data like orders and addresses. The app was not approved and the reasons cited by the reviewer were: The app uses a third-party login service, but does not appear to offer as an equivalent login option another login service with all of the following features: The login option limits data collection to the user’s name and email address. The login option allows users to keep their email address private from all parties as part of setting up their account. The login option does not collect interactions with the app for advertising purposes without consent. Note that Sign in with Apple is a login service that meets all the requirements specified in guideline 4.8. I would like to receive a confirmation that Shopify's new login system is considered a third party login and that it requires the provision of Apple Login as an alternative. The issue with that is that Shopify Customer Account login differs from other 3rd party providers, where you can use them to authenticate, but store data in your own platform afterwards. In Shopify's case, the data that the app needs resides in their platform. We have currently disabled the Shopify login and we could provide Sign in with Apple, if that's needed for compliance, but it would serve no purpose as it wouldn't provide anything more to the users, than our current guest account. Looking forward for a clarification on that issue.

Hello Apple Staff, I’m posting again because this issue has not been resolved yet. We currently have two active apps under the same developer account that are still in Waiting for Review. For one of the affected apps, the details are as follows: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 We also tried to submit an expedited review request, but the expedited review form does not complete successfully. The following error message is displayed: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” Could Apple Staff please check the current status of these review submissions and let us know if any additional action is required from our side? We would greatly appreciate your assistance, as the review process has not started and we are currently unable to submit an expedited review request. Thank you for your time and support.

Hello, I'm a first time developer and both of my submissions for NexFi - Portfolio Tracker have been suck in Waiting for Review for an extended time. TestFlight: My first build was submitted on Feb 15th (25+ days) and still Waiting for Review Production/Distribution: Submitted March 2nd (10 days) and still Waiting for Review. It is a finance category app (portfolio tracker) that requires no login, no account creation, and no server side user data so I figured it should be a relatively quick process as there is a minimal privacy footprint. App Name: NexFi - Portfolio Tracker Platform: iOS App ID: 6759226354

Can not update app privacy information about tracking user after remove the tracking functionality and "NSUserTrackingUsageDescription" from info.plist. Always reminds us App contains "NSUserTrackingUsageDescription"

Hi everyone, I’m wondering if anyone has experienced something similar. My app was already under review, and on June 10 I updated the metadata as requested and replied through the Resolution Center. Since then, the app has remained in “Waiting for Review” for 6 days with no status changes. I’ve already contacted Developer Support and submitted a follow-up request, but haven’t received any updates. Is this normal, or could the review have become stuck in the queue after a metadata update? I’d really appreciate any advice or if Apple Staff could help look into whether this behavior is expected.ID:6774445096 Thank you.

Hello, Our app Hook — Smart Message Assistant has been stuck in “Waiting for Review” since June 9, 2026 — 8 days after resubmission addressing all issues raised under Guideline 3.1.2(c) (Subscriptions). Timeline: • June 8: Rejected under Guideline 3.1.2(c) • June 9: Resubmitted with all issues resolved • June 9 onwards: Stuck in “Waiting for Review” with no movement We have submitted 3 expedited review requests, all approved. We contacted Developer Support via email and through App Store Connect messages with no response. We are a small team with an active marketing campaign dependent on this launch. Every day of delay has direct business impact. Could the App Review team please investigate this submission? Thank you, Eden

Hi everyone, I'm looking for some advice regarding my app review. My app was previously removed from sale by Apple because it had not been updated for a long time. I have now completely updated it, fixed compatibility issues, and submitted a new version. The submission has been in "Waiting for Review" since June 9, and nothing has changed since then. There are no messages in the Resolution Center and no requests for additional information. I understand that apps returning to the App Store may require a full review, but waiting for more than a week without any progress seems unusual. Has anyone experienced a similar situation? Is there anything I can do to have the review started, or should I simply continue waiting? Any advice or feedback would be greatly appreciated. Thank you.

Hi App Review Team, My app Scora is live on the App Store, but both of my auto-renewable subscriptions have been stuck in “In Review” for several weeks. They can’t be purchased in production, and while they are In Review I can’t edit, remove, or re-attach them in App Store Connect. Submitting a new app version since then did not change anything. Could you please either confirm that the subscriptions are correctly attached to my current version submission and will be reviewed together, or reset them to “Ready to Submit” so I can re-attach and resubmit them? Details: App: Scora (App ID: 6737562614) scora.basic_monthly (6756670651) scora.basic_yearly (6756670145) I also didnt get a response to my email request for nearly two weeks. Thats why i reach out here. Thanks a lot for your help!

Hi everyone, I’m trying to get two auto-renewable subscriptions reviewed for my iOS app. Both subscriptions are in the same subscription group. The app binary already includes the subscription screen and the products are visible in the app. The subscription screen shows the subscription title, duration, price, Privacy Policy link, and Terms of Use (EULA) link. However, App Review returned the subscription products with this message: “Guideline 2.1(b) - Performance - App Completeness We have returned the In-App Purchase products as the required binary was not submitted. Once you have resolved all the outstanding issues that were identified and are ready to submit the binary, resubmit the In-App Purchase products with the binary.” What confuses me is that the app binary was already submitted, and all current app versions include these two subscriptions. I also cannot find a separate place on the app version page to attach these subscriptions again. After updating the subscription metadata, I resubmitted the two subscriptions directly from App Store Connect. They are now in “Waiting for Review” status. My questions are: Is it valid to resubmit returned auto-renewable subscriptions directly from the subscription page after the app binary has already been approved or submitted? If App Review says “required binary was not submitted,” where exactly should I attach auto-renewable subscriptions to an app version in the current App Store Connect UI? If the subscriptions are already included in the app binary and are now Waiting for Review, is there anything else I need to do? Thanks.

Hi everyone, I’m wondering if anyone has experienced something similar. I submitted a new consumable In-App Purchase along with an app update. The app update itself was approved and released, but the new IAP has remained in “In Review” for over 8 days now. A few details: The app update was approved without issues. This is a new consumable IAP, but not my first IAP overall. I already have other approved consumable IAPs in the app. There are no messages in the Resolution Center and the status is still “In Review”. The IAP is tied to a World Cup event feature, and the tournament has already started, so the delay is becoming impactful. Has anyone seen an IAP remain in review this long while the associated app version was already approved? Did it eventually get approved, or did you need to contact App Review to move things forward? Thanks in advance for any insights.

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. From 8th of June, I started getting the following error when trying to create external TestFlight builds: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Since then: I cannot create any external TestFlight tests Internal TestFlight builds appear, but cannot be downloaded (“The requested app is not available or doesn’t exist”) This is an individual developer account I am the Account Holder All contracts appear active and valid The issue affects multiple apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!